home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970929-19971216
/
000226_news@newsmaster….columbia.edu _Sat Nov 1 10:33:22 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-15
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA01990
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 1 Nov 1997 10:33:20 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA03001
for kermit.misc@watsun; Sat, 1 Nov 1997 10:33:19 -0500 (EST)
Path: news.columbia.edu!news.new-york.net!news-peer.gip.net!news.gsl.net!gip.net!nntprelay.mathworks.com!news-peer-east.sprintlink.net!news.sprintlink.net!Sprint!uunet!in5.uu.net!news.kersur.net!news.ipswitch!ddl
From: ddl@harvard.* (Dan Lanciani)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: DOS Kermit under W95 (I KNOW it's unforgivable!)
Message-ID: <49762@news.IPSWITCH.COM>
Date: 1 Nov 97 07:32:13 GMT
References: <34591E72.3FBD@SpaceComputer.Com>
Organization: Internet
Lines: 33
Xref: news.columbia.edu comp.protocols.kermit.misc:8006
In article <34591E72.3FBD@SpaceComputer.Com>, Kendall@SpaceComputer.Com (Wm. B. Kendall) writes:
| I am running DOS Kermit 3.14, Patch Level 9, because Tektronix 4010
| emulation is a requirement. I want to do this in a DOS window under
| Windows 95. I will connect to the host over our Ethernet. (I made this
| work under OS/2 with a little help from my friends in this group.) My
| problem is that I don't know how to set the port parameters to
| accomplish this under W95 (I have a fossil driver installed under OS/2,
| and SET PORT FOSSIL 4 and connect via ATDT commands as if I were using a
| modem.) Can anyone advise me on this?
Although there are in theory programs similar to your OS/2 fossil-to-telnet
driver for Windows95, the approach taken by most kermit users in this
situation is to run kermit's internal tcp/ip instead. My ndis3pkt shim
(get it from www.danlan.com) will provide kermit with a packet driver
interface on top of standard Microsoft ndis3 card drivers in Windows95.
The one catch(*) is that if you are also running Microsoft's tcp/ip stack
at the same time, you must assign kermit a different IP address.
Dan Lanciani
ddl@harvard.*
(*) There really is a lot more to the catch than this. All sorts of
funny things can happen when you run two tcp/ip stacks in parallel and
I never liked to recommend the practice. However, the number of requests
for this kind of configuration became too huge to ignore, so I started
to pay attention to the details. As it turns out, although there were
some obscure problems early on, most of the time it just worked. I've
since made some minor adjustments to ndis3pkt and there have been no
failure reports in connection with kermit/ndis3pkt use in the past year
or so. Note that this doesn't necessarily generalize to other packet-
driver-based tcp/ip stacks as the success depends on some particular
details of the tcp/ip implementations. Use at your own risk, your mileage
may vary, void where prohibited, etc...